fix(frontend): support Windows shell commands in Claude CLI invocation (ACS-261) #3
+356
−100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes hang on Windows after "Environment override check" log by replacing hardcoded bash commands with platform-aware shell syntax.
Problem
On Windows, the terminal would hang indefinitely after logging "Environment override check" because
buildClaudeShellCommand()was hardcoded to usebash -ccommands that don't exist on Windows.Solution
Windows: Uses cmd.exe/PowerShell compatible syntax:
clsinstead ofclearcallto execute .bat temp filessetfor environment variablesdelfor file cleanup.batextension for temp files with\r\nline endingsUnix/macOS: Preserves existing bash syntax (unchanged):
clear,source,export,rm -f\nline endingsChanges
buildClaudeShellCommand()to detect platform and generate appropriate commandsgenerateTokenTempFileContent()helper for DRYgetTempFileExtension()helper for DRYinvokeClaudeAsync()Test Plan
claude-integration-handler.test.tspassingpath.join(),os.tmpdir())Linear Ticket
Resolves ACS-261